fix(dashboard): honor fixed-offset event timezones - #8649
Conversation
Signed-off-by: pi0n00r <131018595+pi0n00r@users.noreply.github.com>
Signed-off-by: pi0n00r <131018595+pi0n00r@users.noreply.github.com>
4ac7d19 to
4b3751b
Compare
Signed-off-by: pi0n00r <131018595+pi0n00r@users.noreply.github.com>
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
|
Hello there, We hope that the review process is going smooth and is helpful for you. We want to ensure your pull request is reviewed to your satisfaction. If you have a moment, our community management team would very much appreciate your feedback on your experience with this PR review process. Your feedback is valuable to us as we continuously strive to improve our community developer experience. Please take a moment to complete our short survey by clicking on the following link: https://cloud.nextcloud.com/apps/forms/s/i9Ago4EQRZ7TWxjfmeEpPkf6 Thank you for contributing to Nextcloud and we hope to hear from you soon! (If you believe you should not receive this message, you can add yourself to the blocklist.) |
Summary
UTC+/-HH:MMandUTC+/-HHMMTZID values before the dashboard widget compares or formats event start timesProblem
Sabre VObject falls back to PHP's default timezone when a non-IANA fixed-offset TZID such as
UTC-04:00cannot be resolved. The Calendar view can still render the wall time correctly, butCalendarWidgetreceives aDateTimeImmutablecarrying the fallback timezone and emits the wrongsinceIdand relative subtitle.For example,
DTSTART;TZID="UTC-04:00":20260728T111500can be emitted by the dashboard as 11:15 UTC instead of 11:15 at -04:00.Validation
The change is display-only and performs no calendar write.